Optimized multiple digital wallet presentation

ABSTRACT

Methods and systems for facilitating a digital wallet transaction are described herein. A service provider identifies and recommends the most applicable digital wallets for a user based on various factors, such as user location, type and amount of purchase, type of merchant, and/or mood of the user. The service provider may also rank the recommended digital wallets and/or determine how many should be presented to a user. During merchant checkout, the user is presented with the recommended digital wallets, and the user selects one of the digital wallets to fund the purchase.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.14/475,412, filed Sep. 2, 2014, which claims priority to the filing dateof U.S. Provisional Patent Application No. 61/872,826, filed Sep. 2,2013, which is incorporated by reference in its entirety.

BACKGROUND Field of the Invention

The present invention generally relates to facilitating transactions,and more specifically to facilitating digital wallet transactions.

Related Art

An electronic wallet (eWallet), or digital wallet, is a payment systemthat allows an individual to make an electronic commerce transaction,such as an online purchase of items using a computing device, forexample, a mobile computing device. A server-side eWallet is created byan organization for and about an individual consumer, and is maintainedon the organization's servers. Server-side eWallets provide security,efficiency, and added utility for the consumer. Electronic walletsinclude a software component and an information component. Theinformation may include, for example, a user's shipping address, billingaddress, and payment information/credentials including credit cardnumbers, expiration dates, and security numbers. An electronic walletmay or may not include a near field communication (NFC) hardwarecomponent, which allows payment transactions to be performed by swipingor touching a mobile computing device, card, fob, or other hardware ontoor in proximity to an enabled terminal.

Online shopping via mobile devices is often cumbersome to consumers dueto the relatively small screens and lack of ease of text entry, and thecheckout experience may be particularly difficult. This difficulty hasled to a high degree of online shopping cart abandonment on mobiledevices. A variety of electronic wallet providers have come on themarket to attempt to simplify this shopping experience for the consumer.While there will likely be consolidation of these offerings in thefuture, it is also very likely that multiple electronic wallet optionswill be available.

Although each consumer is likely to adopt one digital wallet, merchantswill need to support all major wallets and make them available toconsumers in their purchase flow. Unfortunately, displaying more paymentoptions in a merchant checkout flow has been shown to negatively impactmerchants' conversion rate, for example, by increasing shopping cartabandonment. Consumers are presented with an array of options, most ofwhich are irrelevant to them and possibly unfamiliar to them, resultingin an experience that causes confusion and results in lack of completionof the purchase.

Moreover, it can be difficult for an online merchant to integratemultiple digital wallet providers, because this adds significant cost tothe merchant's software development efforts and adds complexity to themerchant's back-end accounting systems. Thus, there is a need forimproved payment systems and methods that facilitate digital wallettransactions.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 is a block diagram illustrating a system for facilitating adigital wallet transaction according to an embodiment of the presentdisclosure;

FIG. 2 is a flowchart showing a method for facilitating a digital wallettransaction according to an embodiment of the present disclosure;

FIGS. 3A-3B are screenshots of an interface that is displayed to a userduring merchant checkout; and

FIG. 4 is a block diagram of a system for implementing a deviceaccording to an embodiment of the present disclosure.

Embodiments of the present disclosure and their advantages are bestunderstood by referring to the detailed description that follows. Itshould be appreciated that like reference numerals are used to identifylike elements illustrated in one or more of the figures, whereinshowings therein are for purposes of illustrating embodiments of thepresent disclosure and not for purposes of limiting the same.

DETAILED DESCRIPTION

The present disclosure describes methods and systems that allowmerchants to support multiple digital wallets without the associatednegative impact on consumer experience, conversion rate, andimplementation complexity. A service provider, in cooperation withdigital wallet providers, provides a simplified interface for a merchantto support multiple wallets via the service provider's applicationprogramming interface (API).

When a consumer engages in a purchase flow for an integrated merchant,the service provider makes a real-time assessment of the consumer'spurchase profile. This purchase profile can be used to determine themost likely digital wallets applicable to that consumer. The serviceprovider can then provide one or more recommended digital wallets andautomatically tailor the presentation of the merchant payment experiencebased, in some embodiments, on merchant preferences. For example, thedigital wallet determined to be most applicable for a given consumer maybe displayed most prominently to the user (e.g., it may be displayedalone, it may be displayed first in a listing of digital wallets, it maybe displayed first in a limited listing of digital wallets, or it may bedisplayed with a graphical user interface widget, e.g., a drop-down listor list box, that displays the most applicable digital wallet but allowsthe user to click the drop-down control to display alternative digitalwallets from which to choose). The selected digital wallet can be basedon the current transaction, specific consumer purchasing history, andother information that may change the type of digital wallet selectedfor the consumer for different transactions, such as with differentmerchants, different purchases, different purchase amounts, differenttimes of the year for the purchase, etc.

This allows the merchant to support multiple digital wallets for themerchant's overall customer base while providing a customized purchaseexperience tailored to each consumer. Moreover, the service provider canuse real-time analytics to monitor and increase each consumer'sconversion rate. By optimizing wallet presentation across manymerchants, the service provider can provide a much better experiencethan any single merchant could create on its own.

FIG. 1 shows one embodiment of a block diagram of a network-based system100 adapted to facilitate a digital wallet transaction using a userdevice 120 over a network 160. As shown, system 100 may comprise orimplement a plurality of servers and/or software components that operateto perform various methodologies in accordance with the describedembodiments. Exemplary servers may include, for example, stand-alone andenterprise-class servers operating a server OS such as a MICROSOFT® OS,a UNIX® OS, a LINUX® OS, or other suitable server-based OS. It can beappreciated that the servers illustrated in FIG. 1 may be deployed inother ways and that the operations performed and/or the servicesprovided by such servers may be combined or separated for a givenimplementation and may be performed by a greater number or fewer numberof servers. One or more servers may be operated and/or maintained by thesame or different entities.

As shown in FIG. 1, the system 100 includes a user device 120 (e.g., asmartphone), a merchant server or device 130, a digital wallet providerserver 170, and at least one service provider server or device 180(e.g., network server device) in communication over the network 160. Thenetwork 160, in one embodiment, may be implemented as a single networkor a combination of multiple networks. For example, in variousembodiments, the network 160 may include the Internet and/or one or moreintranets, landline networks, wireless networks, and/or otherappropriate types of communication networks. In another example, thenetwork 160 may comprise a wireless telecommunications network (e.g.,cellular phone network) adapted to communicate with other communicationnetworks, such as the Internet.

The user device 120, in one embodiment, may be utilized by the user 102to interact with the merchant server 130, the digital wallet providerserver 170, and/or the service provider server 180 over the network 160.For example, the user 102 may conduct financial transactions (e.g.,account transfers or payments) with the digital wallet provider server170 and/or the service provider server 180 via the user device 120. Theuser device 120, in various embodiments, may be implemented using anyappropriate combination of hardware and/or software configured for wiredand/or wireless communication over the network 160. In variousimplementations, the user device 120 may include at least one of awireless cellular phone, wearable computing device, PC, laptop, etc.

The user device 120, in one embodiment, includes a user interfaceapplication 122, which may be utilized by the user 102 to conducttransactions (e.g., shopping, purchasing, bidding, etc.) with thedigital wallet provider server 180 and/or service provider server 180over the network 160. In one aspect, purchase expenses may be directlyand/or automatically debited from an account related to the user 102 viathe user interface application 122.

In one implementation, the user interface application 122 includes asoftware program, such as a graphical user interface (GUI), executableby a processor that is configured to interface and communicate with theservice provider server 180 via the network 160. In anotherimplementation, the user interface application 122 includes a browsermodule that provides a network interface to browse information availableover the network 160. For example, the user interface application 122may be implemented, in part, as a web browser to view informationavailable over the network 160.

The user device 120, in various embodiments, may include otherapplications 124 as may be desired in one or more embodiments of thepresent disclosure to provide additional features available to user 102.In one example, such other applications 124 may include securityapplications for implementing client-side security features,programmatic client applications for interfacing with appropriateapplication programming interfaces (APIs) over the network 160, and/orvarious other types of generally known programs and/or softwareapplications. In still other examples, the other applications 124 mayinterface with the user interface application 122 for improvedefficiency and convenience.

In various implementations, a user profile may be created using data andinformation obtained from cell phone activity over the network 160. Cellphone activity transactions may be used by the service provider server180 to create at least one user profile for the user 102 based onactivity from the user device 120 (e.g., cell phone). The user profilemay be updated with each financial and/or information transaction (e.g.,payment transaction, purchase transaction, etc.) achieved through use ofthe user device 120. In various aspects, this may include the type oftransaction, the digital wallet used, and/or the location informationfrom the user device 120. As such, the profile may be used forrecognizing patterns of potential fraud, setting transaction limits onthe user, etc.

The user device 120, in one embodiment, may include at least one useridentifier 126, which may be implemented, for example, as operatingsystem registry entries, cookies associated with the user interfaceapplication 122, identifiers associated with hardware of the user device120, or various other appropriate identifiers. The user identifier 126may include one or more attributes related to the user 102, such aspersonal information related to the user 102 (e.g., one or more usernames, passwords, photograph images, biometric IDs, addresses, phonenumbers, social security number, etc.) and banking information and/orfunding sources (e.g., one or more banking institutions, credit cardissuers, user account numbers, security data and information, etc.). Invarious implementations, the user identifier 126 may be passed with auser login request to the digital wallet provider server 170 and/orservice provider server 180 via the network 160, and the user identifier126 may be used by the digital wallet provider server 170 and/or serviceprovider server 180 to associate the user 102 with a particular useraccount maintained by the digital wallet provider server 170 or serviceprovider server 180.

In various implementations, the user 102 is able to input data andinformation into an input component (e.g., a keyboard) of the userdevice 120 to provide user information with a transaction request, suchas a fund transfer request. The user information may include useridentification information.

User device 120, in various embodiments, include a location component128 configured to determine, track, monitor, and/or provide an instantgeographical location of user device 120. In one implementation, thegeographical location may include GPS coordinates, zip-code information,area-code information, street address information, and/or various othergenerally known types of location information. In one example, thelocation information may be directly entered into user device 120 byuser 102 via a user input component, such as a keyboard, touch display,and/or voice recognition microphone. In another example, the locationinformation may be automatically obtained and/or provided by the userdevice 120 via an internal or external monitoring component thatutilizes a global positioning system (GPS), which uses satellite-basedpositioning, and/or assisted GPS (A-GPS), which uses cell towerinformation to improve reliability and accuracy of GPS-basedpositioning. In other embodiments, the location information may beautomatically obtained without the use of GPS. In some instances, cellsignals or wireless signals are used. For example, location informationmay be obtained by checking in using user device 120 via a check-indevice at a location, such as a beacon. This helps to save battery lifeand to allow for better indoor location where GPS typically does notwork.

User device 120, in various embodiments, includes one or more sensors140. User device 120 may use sensors 140 to measure, which may includetracking, monitoring, detecting, quantifying, capturing, and/orotherwise measuring, one or more biometrics. Service provider server 180may receive data relating to the biometrics from sensors 140. Serviceprovider server 180 can then process, analyze, infer from, and/orinterpret the biometric data.

Sensors 140 include, in various embodiments, an accelerometer,gyroscope, heart rate sensor, blood pressure sensor, thermometer, imagesensor, thermal camera and/or microphone. The accelerometer thatmeasures acceleration and the gyroscope that measures orientation may beused together to measure movement, such as an activity of user 102. Theheart rate sensor, blood pressure sensor, and/or thermometer measurevital signs of user 102.

In one aspect, when interfacing with user device, the user 102 may electand/or consent to provide personal information, such as biometricinformation and/or location information, to service provider server 180.User 102 may set or configure the user settings/configuration menu ofthe user device 120 to provide consent to share the personalinformation. In some embodiments, user 102 may be prompted forpermission to release personal information. Accordingly, user 102 mayhave exclusive authority to allow transmission of personal biometricinformation and/or location information from the user device 120 toservice provider server 180.

The one or more merchant servers 130, in various embodiments, may bemaintained by one or more business entities (or in some cases, by apartner of a business entity that processes transactions on behalf ofbusiness entities). Examples of businesses entities include merchantsites, resource information sites, utility sites, real estate managementsites, social networking sites, etc., which offer various items forpurchase and payment. In some embodiments, business entities may needregistration of the user identity information as part of offering itemsto the user 102 over the network 160. As such, each of the one or moremerchant servers 130 may include a merchant database 132 for identifyingavailable items, which may be made available to the user device 120 forviewing and purchase by the user 102. In one or more embodiments, user102 may complete a transaction such as purchasing the items via digitalwallet provider server 170 or service provider server 180.

Each of the merchant servers 130, in one embodiment, may include amarketplace application 134, which may be configured to provideinformation over the network 160 to the user interface application 122of the user device 120. For example, user 102 may interact with themarketplace application 134 through the user interface application 122over the network 160 to search and view various items available forpurchase in the merchant database 132.

Each of the merchant servers 130, in one embodiment, may include atleast one merchant identifier 136, which may be included as part of theone or more items made available for purchase so that, e.g., particularitems are associated with particular merchants. In one implementation,the merchant identifier 136 may include one or more attributes and/orparameters related to the merchant, such as business and bankinginformation. The merchant identifier 136 may include attributes relatedto the merchant server or device 130, such as identification information(e.g., a serial number, a location address, GPS coordinates, a networkidentification number, etc.). In various embodiments, user 102 mayconduct transactions (e.g., searching, selection, monitoring,purchasing, and/or providing payment for items) with each merchantserver 130 via the digital wallet provider server 170 or serviceprovider server 180 over the network 160.

A merchant website may also communicate (for example, using merchantserver 130) with the digital wallet provider and/or service providerthrough the digital wallet provider server 170 or the service providerserver 180, respectively, over network 160. For example, the merchantwebsite may communicate with the service provider in the course ofvarious services offered by the service provider to a merchant website,such as payment intermediary between customers of the merchant websiteand the merchant website itself. For example, the merchant website mayuse an application programming interface (API) that allows it to offersale of goods in which customers are allowed to make payment through theservice provider, while user 102 may have an account with the serviceprovider that allows user 102 to use the service provider for makingpayments to merchants that allow use of authentication, authorization,and payment services of the service provider as a payment intermediary.The merchant website may also have an account with the service provider.

The digital wallet provider server 170, in one embodiment, may bemaintained by a business entity that provides digital wallets (e.g.,Google®, Apple, Amazon®, MasterCard®, Square®, PayPal®, etc.), a partnerof that business entity, and/or by an online service provider. Digitalwallet provider server 170 maintains one or more accounts in an accountdatabase 172, each of which may include account information 174associated with individual users (e.g., user 102). For example, accountinformation 174 may include user financial account information such ascredit cards, bank accounts, etc. Digital wallet provider server 170 maycommunicate financial information to user device 120, merchant server130, and/or service provider server 180.

The digital wallet provider server 170, in one embodiment, utilizes apayment processing application 176 to process purchases and/or paymentsfor financial transactions between the user 102 and a merchant. Thedigital wallet provider server 170 may have access to informationassociated with a user's credit cards and spending cards. In variousembodiments, the digital wallet provider server 170 acts as anintermediary between a credit card company, the user 102, and amerchant, to process a purchase made with a credit card and generate areceipt for the user device 120.

The service provider server 180, in one embodiment, may be maintained bya transaction processing entity or an online service provider, which mayprovide processing for financial transactions and/or informationtransactions between the user 102 and one or more merchants. As such,the service provider server 180 includes a service application 182,which may be adapted to interact with the user device 120 over thenetwork 160 to facilitate the searching, selection, purchase, and/orpayment of items by the user 102 from one or more merchants. In oneexample, the service provider server 180 may be provided by PayPal®,Inc., eBay® of San Jose, Calif., USA, and/or one or more financialinstitutions or a respective intermediary that may provide multiplepoint of sale devices at various locations to facilitate transactionroutings between merchants and, for example, financial institutions.

The service application 182, in one embodiment, utilizes a paymentprocessing application 184 to process purchases and/or payments forfinancial transactions between the user 102 and a merchant. In oneimplementation, the payment processing application 184 assists withresolving financial transactions through validation, delivery, andsettlement. As such, the service application 182 in conjunction with thepayment processing application 184 settles indebtedness between the user102 and a merchant, wherein accounts may be directly and/orautomatically debited and/or credited of monetary funds in a manner asaccepted by the banking industry.

The service provider server 180, in one embodiment, may be configured tomaintain one or more user accounts and merchant accounts in an accountdatabase 192, each of which may include account information 194associated with one or more individual users (e.g., user 102) andmerchants. For example, account information 194 may include privatefinancial information of user 102 and merchants, such as one or moreaccount numbers, passwords, credit card information, bankinginformation, digital wallets used, or other types of financialinformation, which may be used to facilitate financial transactionsbetween user 102, and one or more merchants. In certain embodiments,account information 194 also includes user purchase profile informationsuch as account funding options and payment options associated with theuser 102 (e.g., various digital wallets used by the user), paymentinformation, receipts, and other information collected in response tocompleted fundings and/or transactions. In various aspects, the methodsand systems described herein may be modified to accommodate users and/ormerchants that may or may not be associated with at least one existinguser account and/or merchant account, respectively.

User purchase profile information may be compiled or determined in anysuitable way. In some instances, some information is solicited when auser first registers with a service provider. The information mightinclude demographic information, a survey of purchase interests, and/ora survey of past purchases. In other instances, information may beobtained from other databases. In certain instances, information aboutthe user and products purchased are collected as the user shops andpurchases various items.

In one implementation, the user 102 may have identity attributes storedwith the service provider server 180, and user 102 may have credentialsto authenticate or verify identity with the service provider server 180.User attributes may include personal information, banking informationand/or funding sources. In various aspects, the user attributes may bepassed to the service provider server 180 as part of a login, search,selection, purchase, and/or payment request, and the user attributes maybe utilized by the service provider server 180 to associate user 102with one or more particular user accounts maintained by the serviceprovider server 180.

In various embodiments, the service provider server 180 includes adigital wallet application 186. The digital wallet application 186receives purchase requests from merchants, identifies digital walletsassociated with user 102, determines which digital wallets are mostapplicable to user 102, and provides merchants with the most applicabledigital wallets. Determination of which wallets should be presented tothe user 102 can depend on a variety of factors, such as user location,type and amount of purchase, type of merchant, and/or mood of the user.In certain embodiments, the service provider server 180 ranks thedigital wallets in order of most applicable to least applicable, andanalyzes how many of the digital wallets should be presented.

Referring now to FIG. 2, a flowchart 200 of a method for facilitating adigital wallet transaction is illustrated according to an embodiment ofthe present disclosure. The user 102 goes through a conventionalcheckout process. For example, the user 102 may access a merchant site,seller site, marketplace site, or other site or mobile app that enablesa user to shop and make a purchase. Access may be through a PC,computing tablet, smart phone, wearable computing device, or othercomputing device. The purchase may be items, physical goods, digitalgoods, donations, services, etc.

The user 102 then selects desired items for purchase from a merchant.Note that items, as used herein, may include one or more of thedifferent purchases listed above. The selected items may be placed in acart, which the user 102 can review and edit if needed. The user 102continues by entering information for the purchase, such as name,address, shipping address, etc.

Once the requested information has been entered or provided, the user102 may confirm the order. Before confirmation, the user 105 may bepresented with details of the purchase, such as item description, itemprices, total price, shipping costs, tax, etc. If the details areacceptable and correct, the user 105 may select a “Confirm,” “Pay,” orother button or link to confirm the order and checkout.

At step 202, the merchant associated with the purchase sends a purchaserequest to the service provider server 180. The request asks for paymentinformation and/or funding information. The purchase request can alsoinclude information regarding the purchase, such as name and/ordescription of each product or service, price for each product, totalprice, etc., and information regarding the merchant, such as merchantname, payment methods accepted by the merchant, acceptable fundingmethods, etc.

At step 204, the service provider server 180 receives the request andidentifies one or more digital wallets associated with user 102. Forexample, the service provider may access the user's purchase profile indatabase 192 to retrieve the digital wallets the user 102 has used inthe past.

At step 206, the service provider server 180 determines one or morerecommended digital wallets from the one or more identified digitalwallets. In several embodiments, the service provider also prioritizesor ranks the digital wallets so that the most applicable digital walletis made more prominent than the other wallets. In some embodiments, theservice provider also decides how many digital wallets should bepresented.

One or more criteria can be used by the service provider to determinewhich digital wallet(s) should be recommended for a given user. Forexample, one or more user identification mechanisms can be used, e.g.,on-device cookies, device fingerprinting, on-device state saved withspecific applications, on-device state saved to globally accessiblestorage, and/or identity information provided by the merchant or user aspart of the purchase flow and payment credential information.Additionally or alternatively, the criteria may include a user'sauthentication with one or more major online identity(ies) providerssuch as Google®, Facebook®, etc. The major internet identity providersare likely to provide digital wallets with significant adoption. Even inthe case that the user does not use a wallet associated with an identityprovider, this identity can be helpful in selecting an appropriatewallet across different interactions. Additionally or alternatively, thecriteria may include a consumer's authentication with an intermediaryparty that provides an online retailer with a software library forbuilding a computing device application (e.g., mobile application)including a sub-application directed toward enabling electronicapplications via the intermediary party (e.g., payment gateway), forexample, consumer authentication with Venmo®, or consumer's use of VenmoTouch™, as described in U.S. patent application Ser. No. 13/755,262,incorporated by reference herein in its entirety. Additionally oralternatively, the criteria may include purchase trends for the merchantknown to the service provider. Additionally or alternatively, thecriteria may include consumer device or browser type, location, orlanguage. Additionally or alternatively, the criteria may include theconsumer's prior purchase behavior as identified on a network managed bythe service provider. Historical use patterns may also be used todetermine which digital wallet(s) to present. For example, if a usertends to use certain digital wallets in a particular way, this mayreveal a preference that can be set as a default or a default ranking ofdigital wallets.

In several exemplary embodiments, the service provider server 180examines the merchant or business in determining which wallets are themost applicable and should be recommended. For example, a merchantcategory code is typically used to classify the types of goods orservices a merchant provides. A user may want to use a more personaltype of wallet when checking out of one kind of store, and a morebusiness type of wallet when making a more business type purchase.

The service provider can also take into account the amount of thepurchase and type of currency accepted by the merchant. Unusable walletscan be filtered out this way. For example, some wallets can only be usedwith a minimum purchase amount, or may not be used when the purchaseexceeds a maximum amount. Some wallets may support all types of currency(e.g., coupons, gift cards, reward points, credit cards, bank accounts,etc.), while some digital wallets do not.

The service provider may also look into consumer deals. Wallet providerscan partner with merchants to provide deals in some circumstances topromote their wallet. For example, the service provider can examine howdifferent digital wallets affect reward programs, perks, discounts,spending limits, etc. The service provider can select digital walletsbased on which wallets are most advantageous to the user.

Yet another factor a service provider may consider is merchant fees. Forexample, the service provider may determine that the most applicabledigital wallets are those that include a merchant fee that does notexceed a specific amount. A merchant can also choose to lower fees ontheir part and allow the service provider to factor that into the orderthat the service provider displays wallets in.

In several exemplary embodiments, the service provider analyzesinformation about the user 102 and user device 120. For example, somedigital wallets are supported on certain user devices, while others arenot.

In some embodiments, the service provider server 180 determines orreceives the location of the user 102 via the user device 120.Information on location may be used to, for example, eliminate digitalwallets that are not accepted at a particular location. Locationinformation may also be used to make suggestions or send coupons orother deals to the user 102. In one example, if the user 102 is close toa store, the service provider may prioritize a wallet that can interactwith the physical store more easily, which in some cases may increaseconversion. In another example, the service provider can use, forinstance, Bluetooth Low Energy (BLE) to determine who is around the user102 and infer the setting that the user is in. The setting, in turn, canbe used to determine if the user is in a chaotic (e.g., kid's birthdayparty) or calm environment (e.g., a seminar or conference), which canhelp the service provider decide what digital wallets (more secure vs.less secure) and how many digital wallet options should be displayed.

In an embodiment, the service provider determines the mode oftransportation the user 102 is on. For example, a user in a car or busis more likely to have access to Wi-Fi than a user on a plane. Thus, theservice provider may decide that more digital wallet options should bedisplayed to the user in a car or bus because the user is likely to bein less of a hurry because he or she does not need to pay for a networkconnection. On the other hand, a user on a plane most likely has to payfor the network connection so he or she will likely just want to see themost applicable digital wallet, rather than several options.

In another embodiment, the time and date the purchase is made is used bythe service provider in its determination. For example, a user who isbuying something at 2 AM on a weekend or on Christmas Eve may not beinterested in seeing a lot of wallet options and may want to use a moresecure wallet. On the other hand, a user who is making a purchase atnoon on a weekday may have more time to decide which digital wallet touse and may be interested in seeing several wallet options.

In certain embodiments, the weather is taken into consideration. Forexample, if the user 102 is buying a cold drink, and the weather isextremely hot, the service provider can infer that the user 102 islikely in a hurry and not interested in seeing several wallet options.On the other hand, if the weather is more pleasant, the user 102 islikely to be more willing to take his or her time to decide which walletoptions to select.

In other embodiments, a user's heart-rate and other biometrics can beused to infer how a user is feeling or his or her mood. Usingbiometrics, such as heart rate and blood pressure, the service providercan infer if the user is excited or nervous. If a user is overly excitedor nervous, the service provider can decide that the user is not in thestate of mind to make a decision so the service provider determines thatonly the most applicable digital wallet should be presented.

In various embodiments, biometric information and sentiment analysis ofthe user's social network activity can also inform the service providerwhat the user is open to. For example, if service provider knows thatuser 102 is happy and posting a lot on social networks, the serviceprovider may determine that the user 102 is willing to try or use adigital wallet that the user does not typically use. For instance, amerchant may want to promote Venmo® since it's likely that the user 102will share a good buying experience on Venmo® and get the merchant alittle bit of advertisement.

In some cases, the service provider may detect suspicious activityacross a payment network that it believes is related to the user 102.The activity may not rise to the level such that traditional securitymeasures are taken. In this example, the service provider can prioritizemore secure wallets to help stop fraud before it happens.

The service provider can make the determination, in some embodiments,based on how fast the user 102 is moving through the interface of theuser device 120. This information can help the service provider guess ifit's better to show the user a single wallet option or multiple walletoptions. If the user 102 is slowly browsing and carefully adding itemsto the cart, the user 102 is likely to want more control and to see moreoptions when selecting a wallet.

In some embodiments, a merchant's preferences are used to determinewhich digital wallets are most applicable to the user 102. For instance,a merchant can configure the wallets displayed and the preferred orderof wallets in real-time by logging in to a service provider controlpanel in cases where the service provider cannot make a smart decisionregarding the digital wallets.

Any and all of the data described above can be used by the serviceprovider to suggest ways to the merchant to increase conversion rates.For example, if a user's surroundings and location are known, theservice provider could use this information to prompt a store worker tocome up and check out the customer personally or to provide coupons ordeals directly to the customer. In another example, if the user 102′spast purchases show that the user 102 is a loyal customer of themerchant or if the user's current purchase exceeds a certain amount, theservice provider may inform the merchant that free shipping should beoffered.

At step 208, the service provider server 180 provides the merchant withthe one or more recommended digital wallets to present to the user 102for the purchase request. In some embodiments, the service providerindicates how many of the digital wallets should be displayed and/or inwhat order. In certain embodiments, the service provider server 180provides instructions to the merchant for presenting the one or morerecommended digital wallets in a customized display.

At step 210, the merchant presents the checkout page to the user 102with the one or more recommended digital wallets. The merchant checkoutpage allows the user 102 to select from the multiple funding optionsand/or payment options to use as funding for the purchase. Thetransaction is then routed to the digital wallet selected by the user102 from the multiple digital wallets. In some embodiments, only onedigital wallet may be presented.

FIGS. 3A and 3B are screenshots of a checkout page 300 from an onlinemerchant's purchase flow for presentation on a user device 120, wherethe merchant supports multiple electronic wallets, and the checkout pageis optimized to present multiple digital wallets that have beenrecommended to the user. In FIG. 3A, two digital wallets 305 (PayPal®and Coinbase®) are prioritized in a horizontal bar and are the onlydigital wallets displayed, although additional wallets are availablewhen the user presses the “more” button. A user can also choose to inputpayment card information.

FIG. 3B illustrates a screenshot 300 of multiple digital wallets 305that are displayed vertically. In this example, the service providerdetermined that PayPal®, Coinbase®, Venmo®, Google®, and Square® are themost applicable digital wallets and that all should be presented asoptions to the user 102. As shown, the payment options include theelectronic wallet names and their associated logos for easyidentification by the user 102. In various embodiments, the best or mostapplicable digital wallet may be displayed more prominently to the user,such as by highlighting, placing it first in the list of paymentoptions, making it larger, etc.

In some embodiments, when the merchant receives the one or morerecommended digital wallets, the presentation of the one or more digitalwallets in the merchant purchase flow (e.g., on the checkout page) isgoverned by merchant preference. For example, the presentation mayaccount for a merchant preference to differentiate the one or morerecommended digital wallets for the given consumer from other digitalwallets recognized by that merchant by highlighting one or more widgetsrepresenting the most applicable wallets in relation to displayedwidgets of the other supported wallets. For example, one or more widgetsrepresenting the highlighted wallets may be the top-most widget(s), thelargest widget(s), the widget(s) with largest font, and/or the widget(s)that is/are otherwise spatially and/or graphically emphasized inrelation to the one or more widgets representing the merchant's othersupported electronic wallets on one or more pages of the merchantpurchase flow. If more than one digital wallet is determined as likelyto be applicable for a given consumer, the widgets representing thewallets may be displayed spatially, in order of descending likelihood ofapplicability for the given consumer (e.g., the widget for the mostlikely wallet on top, the widget for the next likely wallet below that,etc.). Additionally or alternatively, the presentation of digitalwallets may account for a merchant preference to show only the singlemost likely wallet determined to be used by the given consumer. A widgetrepresenting this identified wallet may include a drop-down list or listbox that, upon clicking by the user, displays one or more other walletssupported by the merchant, but having less likelihood to be applicableto the given consumer. Additionally or alternatively, the presentationof digital wallets may account for a merchant preference to show onlythe N most likely wallets determined to be used by the given consumer(e.g., where N is 2, 3, 4, 5, etc.). Additionally or alternatively, thepresentation of digital wallets may account for a merchant preference toshow all supported wallets (or no supported wallets) if there is nostrong signal, e.g., if it cannot be determined which wallet(s) arelikely applicable for the given consumer.

The systems and methods described herein provide a consumer with thedigital wallet options that are most applicable to the consumer, whichcan increase shopping cart conversion. The digital wallet options aretailored to the consumer so that the consumer can receive the bestpurchase experience.

FIG. 4 is a block diagram of a computer system 400 suitable forimplementing one or more embodiments of the present disclosure,including the user device 120, the merchant device or server 130,digital wallet provider server 140, and the service provider server 180.In various implementations, the user device 120 may include a mobilecellular phone, personal computer (PC), laptop, wearable computingdevice, etc. adapted for wireless communication, and the, merchantdevice or server 130, digital wallet provider server 170, and serviceprovider server 180 may include a network computing device, such as aserver. Thus, it should be appreciated that the devices 120, 130, 140,and 180 may be implemented as computer system 400 in a manner asfollows.

Computer system 400 includes a bus 412 or other communication mechanismfor communicating information data, signals, and information betweenvarious components of computer system 400. Components include aninput/output (I/O) component 404 that processes a user (i.e., sender,recipient, service provider) action, such as selecting keys from akeypad/keyboard, selecting one or more buttons or links, etc., and sendsa corresponding signal to bus 412. I/O component 404 may also include anoutput component, such as a display 402 and a cursor control 408 (suchas a keyboard, keypad, mouse, etc.). The display 402 may be configuredto present a checkout page that includes multiple digital wallets. Anoptional audio input/output component 406 may also be included to allowa user to use voice for inputting information by converting audiosignals. Audio I/O component 406 may allow the user to hear audio. Atransceiver or network interface 420 transmits and receives signalsbetween computer system 400 and other devices, such as another userdevice, a merchant server, or a service provider server via network 422.In one embodiment, the transmission is wireless, although othertransmission mediums and methods may also be suitable. A processor 414,which can be a micro-controller, digital signal processor (DSP), orother processing component, processes these various signals, such as fordisplay on computer system 300 or transmission to other devices via acommunication link 424. Processor 414 may also control transmission ofinformation, such as cookies or IP addresses, to other devices.

Components of computer system 400 also include a system memory component410 (e.g., RAM), a static storage component 416 (e.g., ROM), and/or adisk drive 418. Computer system 400 performs specific operations byprocessor 414 and other components by executing one or more sequences ofinstructions contained in system memory component 410. For example,processor 414 can receive purchase requests from a merchant, process thepurchase requests, assess a user's purchase profile, increase a user'sconversion rate, identify digital wallets of a user, determine whichdigital wallets are most applicable to a user and should be recommended,and provide merchants with the recommended digital wallets. Logic may beencoded in a computer readable medium, which may refer to any mediumthat participates in providing instructions to processor 414 forexecution. Such a medium may take many forms, including but not limitedto, non-volatile media, volatile media, and transmission media. Invarious implementations, non-volatile media includes optical or magneticdisks, volatile media includes dynamic memory, such as system memorycomponent 410, and transmission media includes coaxial cables, copperwire, and fiber optics, including wires that comprise bus 412. In oneembodiment, the logic is encoded in non-transitory computer readablemedium. In one example, transmission media may take the form of acousticor light waves, such as those generated during radio wave, optical, andinfrared data communications.

Some common forms of computer readable media includes, for example,floppy disk, flexible disk, hard disk, magnetic tape, any other magneticmedium, CD-ROM, any other optical medium, punch cards, paper tape, anyother physical medium with patterns of holes, RAM, PROM, EPROM,FLASH-EPROM, any other memory chip or cartridge, or any other mediumfrom which a computer is adapted to read.

In various embodiments of the present disclosure, execution ofinstruction sequences to practice the present disclosure may beperformed by computer system 400. In various other embodiments of thepresent disclosure, a plurality of computer systems 400 coupled bycommunication link 424 to the network (e.g., such as a LAN, WLAN, PTSN,and/or various other wired or wireless networks, includingtelecommunications, mobile, and cellular phone networks) may performinstruction sequences to practice the present disclosure in coordinationwith one another.

In view of the present disclosure, it will be appreciated that variousmethods and systems have been described according to one or moreembodiments for facilitating a digital wallet transaction.

Where applicable, various embodiments provided by the present disclosuremay be implemented using hardware, software, or combinations of hardwareand software. Also, where applicable, the various hardware componentsand/or software components set forth herein may be combined intocomposite components comprising software, hardware, and/or both withoutdeparting from the spirit of the present disclosure. Where applicable,the various hardware components and/or software components set forthherein may be separated into sub-components comprising software,hardware, or both without departing from the scope of the presentdisclosure. In addition, where applicable, it is contemplated thatsoftware components may be implemented as hardware components andvice-versa.

Software in accordance with the present disclosure, such as program codeand/or data, may be stored on one or more computer readable mediums. Itis also contemplated that software identified herein may be implementedusing one or more general purpose or specific purpose computers and/orcomputer systems, networked and/or otherwise. Where applicable, theordering of various steps described herein may be changed, combined intocomposite steps, and/or separated into sub-steps to provide featuresdescribed herein.

The various features and steps described herein may be implemented assystems comprising one or more memories storing various informationdescribed herein and one or more processors coupled to the one or morememories and a network, wherein the one or more processors are operableto perform steps as described herein, as non-transitory machine-readablemedium comprising a plurality of machine-readable instructions which,when executed by one or more processors, are adapted to cause the one ormore processors to perform a method comprising steps described herein,and methods performed by one or more devices, such as a hardwareprocessor, user device, server, and other devices described herein.

1. A system, comprising: a non-transitory memory; and one or morehardware processors in communication with the non-transitory memory andconfigured to read instructions from the non-transitory memory to causethe system to perform operations comprising: receiving, via a merchantweb interface displayed on a user device associated with a user, apurchase request related to a purchase from a merchant associated withthe merchant web interface; identifying a user profile associated withthe user device, wherein the user profile comprises user financialinformation related to a plurality of digital wallets associated withthe user; generating a ranking for the plurality of digital wallets forthe purchase request based at least in part on the user profileassociated with the user and the purchase request; deriving an activitycontext for the user based on sensor data obtained from one or moresensors of the user device; determining a maximum number of digitalwallets to be presented to the user based on the derived activitycontext; generating a recommended list of digital wallets comprising anumber of digital wallets selected from the plurality of digital walletsbased on the ranking, wherein the number of digital wallets in therecommended list does not exceed the determined maximum number; andtransmitting, to the merchant web interface displayed on the userdevice, the recommended list of digital wallets to be presented as partof the merchant web interface.
 2. The system of claim 1, wherein eachdigital wallet in the recommended list ranks higher than digital walletsexcluded from the recommended list based on the ranking.
 3. The systemof claim 1, wherein each of the representations of the digital walletsis presented on the merchant web interface with a different spatialand/or graphical emphasis based on the ranking.
 4. The system of claim1, wherein the user profile further comprises information related toprior purchase transactions between the user and a plurality ofmerchants.
 5. The system of claim 1, wherein the operations furthercomprise updating the user profile based on at least one of informationrelated to the merchant, information related to the user, or informationrelated to the user device.
 6. The system of claim 1, wherein the sensordata comprises a detected location of the user device.
 7. The system ofclaim 1, wherein the sensor data comprises biological data associatedwith the user, and wherein the activity context comprises a sentiment ofthe user derived from the biometric data.
 8. The system of claim 7,wherein the biological data comprises at least one of heart rate data,blood pressure data, or body temperature data.
 9. The system of claim 1,wherein the sensor data comprises movement data associated with the userdevice, and wherein the activity context comprises a mode oftransportation used by the user derived from the movement data.
 10. Thesystem of claim 1, wherein the operations further comprise causing therepresentation of at least one digital wallet in the recommended list ofdigital wallets to be presented as highlighted or made larger than theother representations based on the ranking.
 11. The system of claim 1,wherein the operations further comprise updating the user profile withthe purchase request and the derived activity context.
 12. A method forfacilitating a digital wallet transaction, comprising: receiving, by oneor more hardware processors via a merchant web interface displayed on auser device associated with a user, a purchase request related to apurchase from a merchant associated with the merchant web interface;identifying, by the one or more hardware processors, a user profileassociated with the user device, wherein the user profile comprises userfinancial information related to a plurality of digital walletsassociated with a user; generating, by the one or more hardwareprocessors, a ranking for the plurality of digital wallets for thepurchase request based at least in part on the user profile associatedwith the user and the purchase request; deriving, by the one or morehardware processors, an environmental context for the user based onsensor data obtained from one or more sensors of the user device;determining, by the one or more hardware processors, a maximum number ofdigital wallets to be presented to the user based on the derivedenvironmental context; generating, by the one or more hardwareprocessors, a recommended list of digital wallets comprising a number ofdigital wallets selected from the plurality of digital wallets based onthe ranking, wherein the number of digital wallets in the recommendedlist does not exceed the determined maximum number; and transmitting, bythe one or more hardware processors to the merchant web interfacedisplayed on the user device, the recommended list of digital walletsand machine-readable instructions to cause representations of therecommended list of digital wallets to be presented as part of themerchant web interface.
 13. The method of claim 12, wherein each digitalwallet in the recommended list ranks higher than digital walletsexcluded from the recommended list based on the ranking.
 14. The methodof claim 12, wherein each of the representations of the digital walletsis presented on the merchant web interface with a different spatialand/or graphical emphasis based on the ranking.
 15. The method of claim12, wherein the sensor data comprises a detected location of the userdevice.
 16. The method of claim 12, wherein the sensor data comprisesbiological data associated with the user, and wherein the environmentalcontext comprises a sentiment of the user derived from the biometricdata.
 17. The method of claim 16, wherein the biological data comprisesat least one of heart rate data, blood pressure data, or bodytemperature data.
 18. The method of claim 12, wherein the sensor datacomprises movement data associated with the user device, and wherein theenvironmental context comprises a mode of transportation used by theuser derived from the movement data.
 19. A non-transitorymachine-readable medium stored thereon machine-readable instructionsexecutable to cause a machine to perform operations comprising:receiving, via a merchant web interface displayed on a user deviceassociated with a user, a purchase request related to a purchase from amerchant associated with the merchant web interface; identifying a userprofile associated with the user device, wherein the user profilecomprises user financial information related to a plurality of digitalwallets associated with a user; deriving an activity context for theuser based on sensor data obtained from one or more sensors of the userdevice; determining a maximum number of digital wallets to be presentedto the user based on the derived activity context; generating arecommended list of digital wallets comprising a number of digitalwallets selected from the plurality of digital wallets, wherein thenumber of digital wallets in the recommended list does not exceed thedetermined maximum number; and transmitting, to the merchant webinterface displayed on the user device, the recommended list of digitalwallets and machine-readable instructions to cause representations ofthe recommended list of digital wallets to be presented as part of themerchant web interface.
 20. The non-transitory machine-readable mediumof claim 19, wherein the sensor data comprises movement data associatedwith the user device, and wherein the activity context comprises a modeof transportation used by the user derived from the movement data.